[duckdb] Utility to compare table schemas #1442
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is used to check whether a pre-existing table on disk has a schema equal to the one we want. Did this by introducing various utility classes, including: - ColumnDefinition - TableDefinition - IndexType - SQLUtils Also refactored unit tests to decouple from DuckDB, so that it's easier to test other engines in the future (e.g., SQLite).
FelixGV
commented
Jan 15, 2025
...s/venice-duckdb/src/main/java/com/linkedin/venice/duckdb/DuckDBDaVinciRecordTransformer.java
Outdated
Show resolved
Hide resolved
kvargha
approved these changes
Jan 15, 2025
|
Thanks for the review @kvargha ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is used to check whether a pre-existing table on disk has a schema equal to the one we want.
Did this by introducing various utility classes, including:
Also refactored unit tests to decouple from DuckDB, so that it's easier to test other engines in the future (e.g., SQLite).
How was this PR tested?
New unit tests.
Does this PR introduce any user-facing changes?